Skip to main content
Version: 2.0

Daily Stand Ups

Ever sat in a daily stand-up feeling like you're just checking boxes? You're not alone. As an engineering leader, I’ve seen countless stand-ups devolve into unproductive status reports, leaving teams feeling frustrated and disengaged. The daily stand-up is a ritual in most engineering teams – a quick 15-minute meeting, ostensibly to sync up on progress. But how often does it actually feel valuable?

After 20+ years of experience leading engineering teams, I've seen stand-ups done really well, and spectacularly badly. The key isn’t just having a stand-up, but understanding its purpose and actively working to protect it. It's not a status meeting; it's a team synchronization mechanism, and reclaiming that power can dramatically improve velocity and team health.

The Core Problem: Mistaking Output for Outcome

The biggest mistake I see is treating the stand-up as a report on what people did, instead of focusing on how work is progressing towards a shared goal. We fall into the trap of focusing on output – “I finished the authentication service UI” – rather than outcome – “We’re on track to deliver user authentication by Friday, and I need help unblocking a dependency.”

This distinction is crucial. Focusing on output encourages individual task completion without ensuring that work aligns with overall objectives. It also makes it harder to identify impediments that impact the team's ability to deliver.

The Three Questions: A Foundation, Not a Straitjacket

The traditional three questions – What did I do yesterday? What will I do today? Are there any impediments? – are a good starting point, but only if used thoughtfully.

Here’s how to elevate them:

  • Yesterday: Don't ask what was done, but how did that work contribute to the sprint goal? Frame it as, "How did your work move us closer to our sprint commitment?"
  • Today: Instead of just listing tasks, focus on intentions. "What's the most important thing you will accomplish today to help the team succeed?" This emphasizes ownership and prioritization.
  • Impediments: This is the most important question. Encourage the team to be specific about roadblocks and to phrase them as requests for help. “I’m blocked because I need access to the staging environment. Can someone help me with that?” is far more actionable than “I’m waiting on environment access.”

Beyond the Questions: Fostering a Healthy Stand-up Culture

Even with refined questions, a stand-up can fall flat without a supportive culture. Here are some things I’ve found effective:

  • Timeboxing is Non-Negotiable: Seriously. 15 minutes, max. If discussions veer into detail, move them to a separate “parking lot” meeting after the stand-up.
  • The “Walk the Board” Approach: Instead of individuals reporting, visualize the work on a Kanban or Scrum board. Each person talks about the work they're actively moving through the board. This provides context and highlights dependencies.
  • Focus on the “We”, Not the “I”: Encourage team members to frame their updates in terms of the collective effort. “We’re making good progress on the API integration” versus “I finished the integration tests.”
  • Lead by Example: As a manager, don’t dominate the stand-up. Participate as a team member, and focus on facilitating a productive conversation, not dictating it.
  • Experiment and Iterate: What works for one team might not work for another. Regularly solicit feedback and be willing to adjust the format or approach.

When Stand-ups Need a Break

Even the best-run stand-ups can become stale. Here are a few signs it's time to re-evaluate:

  • Silence or Robotic Responses: If team members are just going through the motions, something's wrong.
  • Constant Problem-Solving: Discussions are consistently getting derailed into detailed troubleshooting.
  • Lack of Engagement: People are disengaged, distracted, or seem reluctant to participate.

In these cases, consider experimenting with alternatives: written stand-ups (asynchronous updates via Slack or email), rotating facilitators, or even temporarily suspending stand-ups to see if the team misses them.

Reclaiming the Stand-up: It's Worth the Effort

The daily stand-up is a powerful tool for improving team communication, aligning effort, and accelerating delivery. But it requires intentionality and a commitment to fostering a healthy team culture.

Don't let your stand-up become an unproductive habit. Reclaim its power by focusing on outcomes, fostering open communication, and continuously adapting to the needs of your team. The benefits – increased velocity, improved collaboration, and a more engaged engineering team – make the effort worthwhile.

Challenge for this week: Try reframing the ‘Yesterday’ question to focus on contributions to the sprint goal. Observe the impact on the conversation.